Map CheckPoint HTTP GET Query Parameters

SoftwareShield CheckPoint™ License Server > CheckPoint License Server Interfaces > HTTP GET URL Interface > Map CheckPoint™ HTTP GET Query Parameters

## Map CheckPoint™ HTTP GET Query Parameters

If you use the simple HTTP GET interface through a third-party (such as a merchant services provider) with which you have no control over the parameter names that are passed to the CheckPoint License Server in the URL, you may need to configure the system to Map CheckPoint HTTP GET Query Parameters from the caller to the CheckPoint server. This allows you to map the callers query string parameter name (which may be anything) to inform the CheckPoint server of the associated parameter values meaning in its own context.

For example, your merchant services provider may call a URL you specify (your CheckPoint Server) as the result of a sale, but among the other query string parameters they pass, they pass a parameter named "OrderID" to identify the order number.
EG: "<URL>?OrderID=U1234567&<other prams>"

The CheckPoint License Server can correctly interpret the value of this parameter as the "Order Number" if you use a Query Parameter Mapping. Other query parameter names can be mapped this way.

Alternatively, if you complete control over the query parameter names you are using in the HTTP interface of the CheckPoint License Server, it may be simpler to use the default values for these parameters.

You can map the following parameters:

1. End User Name - Your client's full name. (default query parameter name: "CPEUNAME")

2. End User Company Name - Your client's company. (default query parameter name: "CPEUCONM")

3. End User Referrer - Where the call to the CheckPoint Server came from. Note that this is the referrer specified in the query string not the referrer fetched from the actual requests header since they may differ. (default query parameter name: "CPEUREF")

4. End User IP - The IP address of the end user. Note that this is the IP specified in the query string not the IP fetched from the actual requests header since they may differ. (default query parameter name: "CPEUIP")

5. End User Address 1, 2 and 3 - these three fields are your client's address. (default query parameter names: "CPEUA1", "CPEUA2", "CPEUA3")

6. End User Phone - your client's phone number. (default query parameter name: "CPEUPH")

7. End User Email - your client's email address. (default query parameter name: "CPEUEM")

8. End User Password - your client's password. (default query parameter name: "CPEUPW")

9. Order Number - An order number from your order processing system which you can use to identify individual orders. (default query parameter name: "CPONO")

10. GSN Parameter - This is a special parameter value used by the CheckPoint server to parse arbitrary other query parameter values when you only have access to one "free-form" parameter value from the third-party. This is commonly the case with merchant services providers. (default query parameter name: "GSN")

Mapping query string parameter values is easily accomplished in the License Managers CheckPoint Server Remote Administrator. See: Add Query Parameter Name Mapping, Edit Query Parameter Name Mapping and Delete Query Parameter Name Mapping

If you do have control over the query string parameter names, there is no need to use a query parameter mapping - you can use the default values that the CheckPoint License Server expects.

### More Information

For examples of how to use a Query Parameter Mapping in the HTTP URL itself to generate a new Serial Number, see: Generating Serial Numbers Dynamically.

For examples of how to use a Query Parameter Mapping in HTTP URL itself to add Activations to an existing Serial Number, see: Adding Activations to Existing Serial Numbers.